Skip to content

More accurate categorizing of some elements #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

SelenIT
Copy link

@SelenIT SelenIT commented Sep 15, 2017

Some elements seems to have incorrect "type". More details in the file change comments.

SelenIT added 3 commits September 15, 2017 08:20
The `<dd>` element can contain non-Phrasing [Flow content](https://html.spec.whatwg.org/multipage/grouping-content.html#the-dd-element) ("block" elements, in HTML4 terms) and can itself appear only in the same places where its `<dt>` counterpart can appear. So the definitions of these elements should probably be treated the same way, and the `<dd>` clearly can't be considered "inline" element
The `<select>` element is categorized as "[Phrasing content](https://html.spec.whatwg.org/multipage/form-elements.html#the-select-element)" (correponding to "Inline" elements in HTML4 terms) and doesn't break a line of text (exactly like, e.g., `<input type="text">`), so it should be categorized the same way.
The `<ruby>` element is part of "Text level semantics" section of the spec and is categorized as "[Phrasing content](https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-ruby-element)" (corresponding to "Inline elements" in HTML4 terms). It doesn't break lines as "block elements" do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant